Summary

Fixes #12 — The agentcore validate command had divergent behavior between CLI and TUI modes, missing schema validations, and duplicated business logic.

Changes

src/cli/commands/validate/action.ts

• Added mcp.json and mcp-defs.json validation — CLI now validates all 5 config files (matching TUI behavior)
• Reports all errors instead of stopping on the first failure — the function now iterates through all files and collects per-file results
• New ValidateFileResult type with per-file { file, success, skipped?, error? } — enables both CLI and TUI to show granular status
• Updated ValidateResult to include a results: ValidateFileResult[] array alongside the existing success/error fields
• Optional files (mcp.json, mcp-defs.json, .cli/state.json) are gracefully skipped when absent

src/cli/commands/validate/command.tsx

• Displays all validation errors (joined by newline) instead of just the first one

src/cli/tui/screens/validate/ValidateScreen.tsx

• Refactored to call handleValidate() from action.ts instead of reimplementing validation logic independently
• Maps ValidateFileResult[] to Step[] for the StepProgress UI component
• Added meaningful next steps: suggests "deploy" and "status" on successful validation (was previously steps={[]})

src/cli/commands/validate/index.ts

• Exports new ValidateFileResult type

src/cli/commands/index.ts

• Added missing registerValidate re-export (consistent with all other commands)

src/cli/commands/validate/__tests__/action.test.ts

• Added 8 new tests covering:
  • mcp.json validation when present
  • mcp.json skipped when absent
  • mcp.json error handling
  • mcp-defs.json validation when present
  • mcp-defs.json skipped when absent
  • mcp-defs.json error handling
  • All errors reported (not just first)
  • All 5 files validated when present
• Updated existing tests to work with new results array in return type
• 20 tests total, all passing

Acceptance Criteria

• agentcore validate validates all 5 config files (agentcore.json, aws-targets.json, mcp.json, mcp-defs.json, .cli/state.json)
• CLI and TUI produce consistent validation results
• TUI validate screen reuses handleValidate() — no duplicated validation logic
• All validation errors are reported (not just the first)
• TUI shows "deploy" as a suggested next step on successful validation
• registerValidate is re-exported from src/cli/commands/index.ts
• Unit tests cover mcp.json and mcp-defs.json validation paths
• Existing integration tests still pass